From MM9745 at att.com Tue Jun 1 14:04:06 2021 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 1 Jun 2021 14:04:06 +0000 Subject: [Airship-discuss] RAID Config Implementation In-Reply-To: References: Message-ID: Refreshing this in post-holiday inboxes: Phil, Craig, Greg, Darren, (& anyone else with experience with RAID config today) – please take a look at my thoughts below and let me know if that lines up with what you would find most useful as well. Thanks! Also, Merging Mahnoor’s comments with the email thread: (quote) Thank you for your email, Matt. About the Airship use cases: 1. The strongly declarative one would be easy to support via Metal3, to the best of my knowledge. This would be perfect as long as the Airship user is okay with finding out the disk and RAID controller names through other means (using iDRAC, for example). It would also be an easier and valuable implementation. 2. Metal3 will perform the disk selection itself (or delegate to Ironic). Providing some level of guarantee for the disk failures would contribute to a reliable user experience. For the declarative case, we can perhaps ensure that the specified disks are functional. For the specification with hints, I suggest making the disk capacity a metric that must always be satisfied (e.g. x GB always provided). Input on these requirements is much appreciated, so we can carry the discussion forward with the Metal3 community and get to implementation. Thank you so much! (end quote) From: MCEUEN, MATT Sent: Wednesday, May 26, 2021 4:17 PM To: Zainub Wahid ; airship-discuss at lists.airshipit.org; SPHICAS, PHIL G ; OBERFIELD, GREG ; DEJAEGER, DARREN R ; STEIN, JARED W Cc: Williams, J T ; Airship ; richard_pioso at dell.com Subject: RE: [Airship-discuss] RAID Config Implementation Thanks for sharing & summarizing this, Zainub. Phil, Craig, Greg, Darren, (& anyone else with experience with RAID config today) – here are my thoughts; please refine/agree/disagree with them so we can give the Metal3 community good feedback on the interface we need for declarative RAID config. First: long term, we want to be able to declaratively configure all the BIOS settings that need to be configured. Steps like this RAID config are a valuable step in that direction. Second: I think there are use cases for both of these setups, and I’d advocate for M3 facilitating both of them in the long run*: 1. Strongly declarative: I want a RAID-N array on ControllerX with disks [DiskY, DiskZ] 2. Declarative with hints: I want a RAID-N array with two SSDs (and I don’t care what disk or what controller – you figure it out, M3!) * Rook supports something similar – “use all disks:yes/no”, or alternately “use these specific disks:…” Third: I think that #1 is a good fit for our most common use cases, where we put a lot of work into a reference definition, and then stamp it out many times on identical hardware. This is also the simplest implementation and would probably get something usable into Airship’s hands fastest. Does that sound right to you all? The other thing to consider is thresholding when disks are bad. I.e. a config item that says something like, “tolerate disk failures as long as I get Xgb” or “as long as I get 3 disks” or something. Do you think this is critical enough to be needed on Day 1? Thanks! Matt From: Zainub Wahid > Sent: Tuesday, May 25, 2021 11:50 AM To: airship-discuss at lists.airshipit.org Cc: Williams, J T >; Airship >; richard_pioso at dell.com Subject: [Airship-discuss] RAID Config Implementation Hello everyone, As discussed in today's meeting, this is related to the demo represented by Noor, last year, related to performing RAID configurations in Airship via Metal3 (and Ironic). Add RAID to example hardwareprofile (I50c82ce5) · Gerrit Code Review (opendev.org) Through Airship, the user should be able to perform RAID configurations on their hardware. The user can specify the RAID controller names and their associated disks, along with the required RAID level, the desired number of disks and the amount of storage required. Here is the proposal for specifying the RAID configuration for a bare metal host via Metal3: https://github.com/metal3-io/metal3-docs/pull/148/files In terms of the CRD, the current implementation of the RAID has the following sections in it, for hardware RAID: spec: raid: hardwareRAIDVolumes: - sizeGibiBytes: 1000 level: 1 name: volume-name rotational: true numberOfPhysicalDisks: 2 We propose to add fields into the CRD, in the following manner: spec: raid: hardwareRAIDVolumes: - sizeGibiBytes: 1000 level: 1 name: volume-1 rotational: true numberOfPhysicalDisks: 2 physicalDisks: - diskName: Disk-1 - diskName: Disk-2 controller: primary-controller - sizeGibiBytes: 2000 level: 0 name: volume-2 rotational: false numberOfPhysicalDisks: 2 physicalDisks: - diskName: Disk-3 - diskName: Disk-4 controller: secondary-controller-2 However, it remains unclear how the user would have the in-depth knowledge of the RAID controllers available to them, along with the vendor-specific disk names. Example disk names (Dell): ['Disk.Bay.0:Enclosure.Internal.0-1:RAID.Intergrated.1-1', 'Disk.Bay.2:Enclosure.Internal.0-1:RAID.Integrated.1-1', 'Disk.Bay.3:Enclosure.Internal.0-1:RAID.Integrated.1-1',...] Example disk names (HP): ['2I:1:1', '2I:1:2', '2I:1:3',...] Example RAID Controllers (Dell): [‘Boss-F1 RAID Controller’, 'Dell PowerEdge RAID Controller H740P', ' Dell PowerEdge RAID Controller H830',...] Example RAID controller (HP): ['HP Smart Array P400 Controller', 'HPE Smart Array E208i-a Controller', 'HPE Smart Array P816i-a Controller',...] One possible solution is to let the user specify the required RAID level, number of disks and storage capacity needed. Metal3 could then validate this request using the Ironic drivers (e.g. Redfish driver, iDRAC driver etc.) in order to ensure the required hardware is available in the cluster. If it is available, the RAID configuration can be applied. Ifnot, the user can be informed about the error. Another solution is that Airship can perform inventory of the storage subsystems available in the cluster, and so the user can construct a RAID configuration accordingly. Conversely, the logic to select the physical disks and associated controllers may be implemented in Airship, whilst the user just specifies the high level requirements. One issue is that Redfish requires the explicit RAID controller and disk names in order to do the RAID configuration, but it would be more convenient if the user did not have to know the low level details of their system. Here is the Redfish Action URI: {Base URI of target resource}/Actions/Volume.ChangeRAIDLayout (Provided in 6.109.4.2 of Redfish Resource and Schema Guide (dmtf.org)) The disk names can be generated using the Redfish logic constructing a human friendly identifier or label for hardware devices. https://github.com/DMTF/Redfish-Tacklebox/blob/e429f70a79cfe288756618498ce485ab4be37131/redfish_utilities/inventory.py#L192 Disk selection logic needs to be implemented in the most appropriate place. Airship may require that the user be unaware of the storage subsystem details when requesting the RAID config. Ironic requires a vendor independent implementation for this purpose. Here is relevant work done in metal3 to support RAID configuration in baremetal servers, using the Fujitsu iRMC driver: https://github.com/metal3-io/baremetal-operator/issues/206 https://github.com/metal3-io/baremetal-operator/pull/292 Warm Regards, Zainub Wahid Network Design Engineer II, xFlow Research Inc. +923044506900 zainub.wahid at xflowresearch.com www.xFlowResearch.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From zainub.wahid at xflowresearch.com Thu Jun 3 10:49:43 2021 From: zainub.wahid at xflowresearch.com (Zainub Wahid) Date: Thu, 3 Jun 2021 15:49:43 +0500 Subject: [Airship-discuss] RAID Config Implementation In-Reply-To: References: Message-ID: Darren, Thank you so much for your time and reply. These are very helpful and important points you mentioned in your email. For [1], we are already taking care of this. Exceptions will be thrown if there is any problem with Disks. For [2], it seems a very interesting point but according to my knowledge, these are OS level configurations. We will look into it in future but right now, it is beyond our scope. Thank you for showing interest, once again. Warm Regards, Zainub Wahid Network Design Engineer II, xFlow Research Inc. +923044506900 zainub.wahid at xflowresearch.com www.xFlowResearch.com On Tue, Jun 1, 2021 at 7:20 PM DEJAEGER, DARREN R wrote: > Matt, > > > > I agree with your thoughts on making available both approaches. A couple > things to consider: > > > > 1. Regarding disk failures: would these disks even be available to be > selected for any sort of RAID if they’re bad? If not, we’d quickly hit an > issue with a mismatched number of disks vs. what’s declared (at least > today). > 2. Can we allow other disk/raid-related config to be tuned? I’m > thinking Stripe size, Read policy, Write policy? > > > > Just some food for thought. > > > > Regards, > > Darren > > > > *From: *"MCEUEN, MATT" > *Date: *Tuesday, June 1, 2021 at 10:04 AM > *To: *Zainub Wahid , " > airship-discuss at lists.airshipit.org" , > "SPHICAS, PHIL G" , "OBERFIELD, GREG" , > "DEJAEGER, DARREN R" , "STEIN, JARED W" > *Cc: *"Williams, J T" , Airship < > airship at xflowresearch.com>, "richard_pioso at dell.com" < > richard_pioso at dell.com> > *Subject: *RE: [Airship-discuss] RAID Config Implementation > > > > Refreshing this in post-holiday inboxes: Phil, Craig, Greg, Darren, (& > anyone else with experience with RAID config today) – please take a look at > my thoughts below and let me know if that lines up with what you would find > most useful as well. Thanks! > > > > > > Also, Merging Mahnoor’s comments with the email thread: > > (quote) > > Thank you for your email, Matt. > > > > About the Airship use cases: > > 1. The strongly declarative one would be easy to support via Metal3, to > the best of my knowledge. This would be perfect as long as the Airship user > is okay with finding out the disk and RAID controller names through other > means (using iDRAC, for example). It would also be an easier and valuable > implementation. > > 2. Metal3 will perform the disk selection itself (or delegate to Ironic). > > > > Providing some level of guarantee for the disk failures would contribute > to a reliable user experience. For the declarative case, we can perhaps > ensure that the specified disks are functional. For the specification with > hints, I suggest making the disk capacity a metric that must always be > satisfied (e.g. x GB always provided). > > > > Input on these requirements is much appreciated, so we can carry the > discussion forward with the Metal3 community and get to implementation. > > Thank you so much! > > (end quote) > > > > *From:* MCEUEN, MATT > *Sent:* Wednesday, May 26, 2021 4:17 PM > *To:* Zainub Wahid ; > airship-discuss at lists.airshipit.org; SPHICAS, PHIL G ; > OBERFIELD, GREG ; DEJAEGER, DARREN R ; > STEIN, JARED W > *Cc:* Williams, J T ; Airship < > airship at xflowresearch.com>; richard_pioso at dell.com > *Subject:* RE: [Airship-discuss] RAID Config Implementation > > > > Thanks for sharing & summarizing this, Zainub. > > > > Phil, Craig, Greg, Darren, (& anyone else with experience with RAID config > today) – here are my thoughts; please refine/agree/disagree with them so we > can give the Metal3 community good feedback on the interface we need for > declarative RAID config. > > > > First: long term, we want to be able to declaratively configure all the > BIOS settings that need to be configured. Steps like this RAID config are > a valuable step in that direction. > > > > Second: I think there are use cases for both of these setups, and I’d > advocate for M3 facilitating both of them in the long run*: > > 1. Strongly declarative: I want a RAID-N array on ControllerX with > disks [DiskY, DiskZ] > 2. Declarative with hints: I want a RAID-N array with two SSDs (and I > don’t care what disk or what controller – you figure it out, M3!) > > * Rook supports something similar – “use all disks:yes/no”, or alternately > “use these specific disks:…” > > > > Third: I think that #1 is a good fit for our most common use cases, where > we put a lot of work into a reference definition, and then stamp it out > many times on *identical* hardware. This is also the simplest > implementation and would probably get something usable into Airship’s hands > fastest. > > > > Does that sound right to you all? > > > > The other thing to consider is thresholding when disks are bad. I.e. a > config item that says something like, “tolerate disk failures as long as I > get Xgb” or “as long as I get 3 disks” or something. Do you think this is > critical enough to be needed on Day 1? > > > > Thanks! > > Matt > > > > *From:* Zainub Wahid > *Sent:* Tuesday, May 25, 2021 11:50 AM > *To:* airship-discuss at lists.airshipit.org > *Cc:* Williams, J T ; Airship < > airship at xflowresearch.com>; richard_pioso at dell.com > *Subject:* [Airship-discuss] RAID Config Implementation > > > > Hello everyone, > > > > As discussed in today's meeting, this is related to the demo represented > by Noor, last year, related to performing RAID configurations in Airship > via Metal3 (and Ironic). > Add RAID to example hardwareprofile (I50c82ce5) · Gerrit Code Review ( > opendev.org > > ) > > Through Airship, the user should be able to perform RAID configurations on > their hardware. The user can specify the RAID controller names and their > associated disks, along with the required RAID level, the desired number of > disks and the amount of storage required. > Here is the proposal for specifying the RAID configuration for a bare > metal host via Metal3: > https://github.com/metal3-io/metal3-docs/pull/148/files > > > In terms of the CRD, the current implementation of the RAID has the > following sections in it, for hardware RAID: > spec: > raid: > hardwareRAIDVolumes: > - sizeGibiBytes: 1000 > level: 1 > name: volume-name > rotational: true > numberOfPhysicalDisks: 2 > We propose to add fields into the CRD, in the following manner: > spec: > raid: > hardwareRAIDVolumes: > - sizeGibiBytes: 1000 > level: 1 > name: volume-1 > rotational: true > numberOfPhysicalDisks: 2 > physicalDisks: > - diskName: Disk-1 > - diskName: Disk-2 > controller: primary-controller > - sizeGibiBytes: 2000 > level: 0 > name: volume-2 > rotational: false > numberOfPhysicalDisks: 2 > physicalDisks: > - diskName: Disk-3 > - diskName: Disk-4 > controller: secondary-controller-2 > > However, it remains unclear how the user would have the in-depth knowledge > of the RAID controllers available to them, along with the vendor-specific > disk names. > Example disk names (Dell): > ['Disk.Bay.0:Enclosure.Internal.0-1:RAID.Intergrated.1-1', > 'Disk.Bay.2:Enclosure.Internal.0-1:RAID.Integrated.1-1', > 'Disk.Bay.3:Enclosure.Internal.0-1:RAID.Integrated.1-1',...] > Example disk names (HP): > ['2I:1:1', '2I:1:2', '2I:1:3',...] > > Example RAID Controllers (Dell): > [‘Boss-F1 RAID Controller’, 'Dell PowerEdge RAID Controller H740P', ' Dell > PowerEdge RAID Controller H830',...] > Example RAID controller (HP): > ['HP Smart Array P400 Controller', 'HPE Smart Array E208i-a Controller', > 'HPE Smart Array P816i-a Controller',...] > > One possible solution is to let the user specify the required RAID level, > number of disks and storage capacity needed. Metal3 could then validate > this request using the Ironic drivers (e.g. Redfish driver, iDRAC driver > etc.) in order to ensure the required hardware is available in the cluster. > If it is available, the RAID configuration can be applied. Ifnot, the user > can be informed about the error. > > Another solution is that Airship can perform inventory of the storage > subsystems available in the cluster, and so the user can construct a RAID > configuration accordingly. Conversely, the logic to select the physical > disks and associated controllers may be implemented in Airship, whilst the > user just specifies the high level requirements. > > One issue is that Redfish requires the explicit RAID controller and disk > names in order to do the RAID configuration, but it would be more > convenient if the user did not have to know the low level details of their > system. > Here is the Redfish Action URI: {Base URI of target > resource}/Actions/Volume.ChangeRAIDLayout > (Provided in 6.109.4.2 of Redfish Resource and Schema Guide (dmtf.org > > )) > > The disk names can be generated using the Redfish logic constructing a > human friendly identifier or label for hardware devices. > https://github.com/DMTF/Redfish-Tacklebox/blob/e429f70a79cfe288756618498ce485ab4be37131/redfish_utilities/inventory.py#L192 > > > Disk selection logic needs to be implemented in the most appropriate > place. Airship may require that the user be unaware of the storage > subsystem details when requesting the RAID config. Ironic requires a vendor > independent implementation for this purpose. > > Here is relevant work done in metal3 to support RAID configuration in > baremetal servers, using the Fujitsu iRMC driver: > https://github.com/metal3-io/baremetal-operator/issues/206 > > https://github.com/metal3-io/baremetal-operator/pull/292 > > > > > > > Warm Regards, > > > > Zainub Wahid > > Network Design Engineer II, > > xFlow Research Inc. > > +923044506900 > > zainub.wahid at xflowresearch.com > > www.xFlowResearch.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at optimcloud.com Thu Jun 3 13:52:28 2021 From: lists at optimcloud.com (Embedded Devel) Date: Thu, 3 Jun 2021 20:52:28 +0700 Subject: [Airship-discuss] Airship 2.0 40Gb Network cards Message-ID: Hi All, Can I inquire as to what 40Gb nic cards work out of the box, We have some intel however they required a manually build / loaded driver, so we need to allocate new cards, whats working ? TIA. From amy at demarco.com Fri Jun 4 21:00:12 2021 From: amy at demarco.com (Amy Marrich) Date: Fri, 4 Jun 2021 16:00:12 -0500 Subject: [Airship-discuss] [Diversity] Diversity and Inclusion Meeting Reminder - OFTC Message-ID: The Diversity & Inclusion WG invites members of all OIF projects to attend our next meeting Monday June 7th, at 17:00 UTC in the #openinfra-diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/ diversity-wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dd118r at att.com Tue Jun 1 14:20:04 2021 From: dd118r at att.com (DEJAEGER, DARREN R) Date: Tue, 1 Jun 2021 14:20:04 +0000 Subject: [Airship-discuss] RAID Config Implementation In-Reply-To: References: Message-ID: Matt, I agree with your thoughts on making available both approaches. A couple things to consider: 1. Regarding disk failures: would these disks even be available to be selected for any sort of RAID if they’re bad? If not, we’d quickly hit an issue with a mismatched number of disks vs. what’s declared (at least today). 2. Can we allow other disk/raid-related config to be tuned? I’m thinking Stripe size, Read policy, Write policy? Just some food for thought. Regards, Darren From: "MCEUEN, MATT" Date: Tuesday, June 1, 2021 at 10:04 AM To: Zainub Wahid , "airship-discuss at lists.airshipit.org" , "SPHICAS, PHIL G" , "OBERFIELD, GREG" , "DEJAEGER, DARREN R" , "STEIN, JARED W" Cc: "Williams, J T" , Airship , "richard_pioso at dell.com" Subject: RE: [Airship-discuss] RAID Config Implementation Refreshing this in post-holiday inboxes: Phil, Craig, Greg, Darren, (& anyone else with experience with RAID config today) – please take a look at my thoughts below and let me know if that lines up with what you would find most useful as well. Thanks! Also, Merging Mahnoor’s comments with the email thread: (quote) Thank you for your email, Matt. About the Airship use cases: 1. The strongly declarative one would be easy to support via Metal3, to the best of my knowledge. This would be perfect as long as the Airship user is okay with finding out the disk and RAID controller names through other means (using iDRAC, for example). It would also be an easier and valuable implementation. 2. Metal3 will perform the disk selection itself (or delegate to Ironic). Providing some level of guarantee for the disk failures would contribute to a reliable user experience. For the declarative case, we can perhaps ensure that the specified disks are functional. For the specification with hints, I suggest making the disk capacity a metric that must always be satisfied (e.g. x GB always provided). Input on these requirements is much appreciated, so we can carry the discussion forward with the Metal3 community and get to implementation. Thank you so much! (end quote) From: MCEUEN, MATT Sent: Wednesday, May 26, 2021 4:17 PM To: Zainub Wahid ; airship-discuss at lists.airshipit.org; SPHICAS, PHIL G ; OBERFIELD, GREG ; DEJAEGER, DARREN R ; STEIN, JARED W Cc: Williams, J T ; Airship ; richard_pioso at dell.com Subject: RE: [Airship-discuss] RAID Config Implementation Thanks for sharing & summarizing this, Zainub. Phil, Craig, Greg, Darren, (& anyone else with experience with RAID config today) – here are my thoughts; please refine/agree/disagree with them so we can give the Metal3 community good feedback on the interface we need for declarative RAID config. First: long term, we want to be able to declaratively configure all the BIOS settings that need to be configured. Steps like this RAID config are a valuable step in that direction. Second: I think there are use cases for both of these setups, and I’d advocate for M3 facilitating both of them in the long run*: 1. Strongly declarative: I want a RAID-N array on ControllerX with disks [DiskY, DiskZ] 2. Declarative with hints: I want a RAID-N array with two SSDs (and I don’t care what disk or what controller – you figure it out, M3!) * Rook supports something similar – “use all disks:yes/no”, or alternately “use these specific disks:…” Third: I think that #1 is a good fit for our most common use cases, where we put a lot of work into a reference definition, and then stamp it out many times on identical hardware. This is also the simplest implementation and would probably get something usable into Airship’s hands fastest. Does that sound right to you all? The other thing to consider is thresholding when disks are bad. I.e. a config item that says something like, “tolerate disk failures as long as I get Xgb” or “as long as I get 3 disks” or something. Do you think this is critical enough to be needed on Day 1? Thanks! Matt From: Zainub Wahid > Sent: Tuesday, May 25, 2021 11:50 AM To: airship-discuss at lists.airshipit.org Cc: Williams, J T >; Airship >; richard_pioso at dell.com Subject: [Airship-discuss] RAID Config Implementation Hello everyone, As discussed in today's meeting, this is related to the demo represented by Noor, last year, related to performing RAID configurations in Airship via Metal3 (and Ironic). Add RAID to example hardwareprofile (I50c82ce5) · Gerrit Code Review (opendev.org) Through Airship, the user should be able to perform RAID configurations on their hardware. The user can specify the RAID controller names and their associated disks, along with the required RAID level, the desired number of disks and the amount of storage required. Here is the proposal for specifying the RAID configuration for a bare metal host via Metal3: https://github.com/metal3-io/metal3-docs/pull/148/files In terms of the CRD, the current implementation of the RAID has the following sections in it, for hardware RAID: spec: raid: hardwareRAIDVolumes: - sizeGibiBytes: 1000 level: 1 name: volume-name rotational: true numberOfPhysicalDisks: 2 We propose to add fields into the CRD, in the following manner: spec: raid: hardwareRAIDVolumes: - sizeGibiBytes: 1000 level: 1 name: volume-1 rotational: true numberOfPhysicalDisks: 2 physicalDisks: - diskName: Disk-1 - diskName: Disk-2 controller: primary-controller - sizeGibiBytes: 2000 level: 0 name: volume-2 rotational: false numberOfPhysicalDisks: 2 physicalDisks: - diskName: Disk-3 - diskName: Disk-4 controller: secondary-controller-2 However, it remains unclear how the user would have the in-depth knowledge of the RAID controllers available to them, along with the vendor-specific disk names. Example disk names (Dell): ['Disk.Bay.0:Enclosure.Internal.0-1:RAID.Intergrated.1-1', 'Disk.Bay.2:Enclosure.Internal.0-1:RAID.Integrated.1-1', 'Disk.Bay.3:Enclosure.Internal.0-1:RAID.Integrated.1-1',...] Example disk names (HP): ['2I:1:1', '2I:1:2', '2I:1:3',...] Example RAID Controllers (Dell): [‘Boss-F1 RAID Controller’, 'Dell PowerEdge RAID Controller H740P', ' Dell PowerEdge RAID Controller H830',...] Example RAID controller (HP): ['HP Smart Array P400 Controller', 'HPE Smart Array E208i-a Controller', 'HPE Smart Array P816i-a Controller',...] One possible solution is to let the user specify the required RAID level, number of disks and storage capacity needed. Metal3 could then validate this request using the Ironic drivers (e.g. Redfish driver, iDRAC driver etc.) in order to ensure the required hardware is available in the cluster. If it is available, the RAID configuration can be applied. Ifnot, the user can be informed about the error. Another solution is that Airship can perform inventory of the storage subsystems available in the cluster, and so the user can construct a RAID configuration accordingly. Conversely, the logic to select the physical disks and associated controllers may be implemented in Airship, whilst the user just specifies the high level requirements. One issue is that Redfish requires the explicit RAID controller and disk names in order to do the RAID configuration, but it would be more convenient if the user did not have to know the low level details of their system. Here is the Redfish Action URI: {Base URI of target resource}/Actions/Volume.ChangeRAIDLayout (Provided in 6.109.4.2 of Redfish Resource and Schema Guide (dmtf.org)) The disk names can be generated using the Redfish logic constructing a human friendly identifier or label for hardware devices. https://github.com/DMTF/Redfish-Tacklebox/blob/e429f70a79cfe288756618498ce485ab4be37131/redfish_utilities/inventory.py#L192 Disk selection logic needs to be implemented in the most appropriate place. Airship may require that the user be unaware of the storage subsystem details when requesting the RAID config. Ironic requires a vendor independent implementation for this purpose. Here is relevant work done in metal3 to support RAID configuration in baremetal servers, using the Fujitsu iRMC driver: https://github.com/metal3-io/baremetal-operator/issues/206 https://github.com/metal3-io/baremetal-operator/pull/292 Warm Regards, Zainub Wahid Network Design Engineer II, xFlow Research Inc. +923044506900 zainub.wahid at xflowresearch.com www.xFlowResearch.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Mon Jun 7 14:56:00 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 7 Jun 2021 14:56:00 +0000 Subject: [Airship-discuss] Thursday Airship Design Meeting Message-ID: Design Topics or Agenda https://hackmd.io/QiEksO4fRk-MnBjwBFaAkQ Recordings https://hackmd.io/CvuF8MzmR9KPqyAePnilPQ ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,127354383# United States, Houston Phone Conference ID: 127 354 383# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 7491 bytes Desc: not available URL: From rp2723 at att.com Mon Jun 7 14:55:47 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 7 Jun 2021 14:55:47 +0000 Subject: [Airship-discuss] Tuesday Airship Open Design Discussions Message-ID: Meetings Topics can be found at : https://hackmd.io/QiEksO4fRk-MnBjwBFaAkQ Airship Notes : https://hackmd.io/team/airship?nav=overview ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,928172342# United States, Houston Phone Conference ID: 928 172 342# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 7184 bytes Desc: not available URL: From rp2723 at att.com Mon Jun 7 14:55:58 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 7 Jun 2021 14:55:58 +0000 Subject: [Airship-discuss] Thursday Airship Design Meeting Message-ID: Design Topics or Agenda https://hackmd.io/QiEksO4fRk-MnBjwBFaAkQ Recordings https://hackmd.io/CvuF8MzmR9KPqyAePnilPQ ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,127354383# United States, Houston Phone Conference ID: 127 354 383# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 7729 bytes Desc: not available URL: From rp2723 at att.com Mon Jun 7 14:55:57 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 7 Jun 2021 14:55:57 +0000 Subject: [Airship-discuss] Thursday Airship Design Meeting Message-ID: Design Topics or Agenda https://hackmd.io/QiEksO4fRk-MnBjwBFaAkQ Recordings https://hackmd.io/CvuF8MzmR9KPqyAePnilPQ ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,127354383# United States, Houston Phone Conference ID: 127 354 383# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 7438 bytes Desc: not available URL: From rp2723 at att.com Mon Jun 7 14:55:59 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 7 Jun 2021 14:55:59 +0000 Subject: [Airship-discuss] Thursday Airship Design Meeting Message-ID: Design Topics or Agenda https://hackmd.io/QiEksO4fRk-MnBjwBFaAkQ Recordings https://hackmd.io/CvuF8MzmR9KPqyAePnilPQ ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,127354383# United States, Houston Phone Conference ID: 127 354 383# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 7491 bytes Desc: not available URL: From MM9745 at att.com Mon Jun 7 20:56:56 2021 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 7 Jun 2021 20:56:56 +0000 Subject: [Airship-discuss] [Working Committee] combining the WC and TC In-Reply-To: References: Message-ID: I’ve captured the proposed changes in a governance patchset: https://review.opendev.org/795182 Feedback is welcome; we’ll discuss in the next Working Committee meeting. From: GU, JAMES Sent: Thursday, May 27, 2021 4:34 PM To: Kostiantyn Kalynovskyi ; WALTERS, ANDREW Cc: MCEUEN, MATT ; KALYNOVSKYI, KOSTIANTYN ; PUNNAPUZHA, SREEJITH ; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] [Working Committee] combining the WC and TC +1 From: Kostiantyn Kalynovskyi > Sent: Thursday, May 27, 2021 2:33 PM To: WALTERS, ANDREW > Cc: MCEUEN, MATT >; GU, JAMES >; KALYNOVSKYI, KOSTIANTYN >; PUNNAPUZHA, SREEJITH >; airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] [Working Committee] combining the WC and TC +1 On Thu, May 27, 2021 at 3:21 PM WALTERS, ANDREW > wrote: > Airship Working Committee, > > With the TC having voted unanimously in favor of merging the TC and WC into a single body with 9 seats, it falls on us to vote and then to update our governance per the outcome. > > Our normal WC meeting would be this following Monday, but that falls on a holiday (so consider this a cancellation notice!). If we'd like to discuss/refine this further before voting I can set up a make-up call next week. > > I propose that we combine the TC and WC into a single body with 9 seats, with the name "Airship Technical Committee". Working Committee members (only), please respond with +1, -1, or "needs discussion". Discussion/approval of the nitty gritty details can be handled via code review on a patchset to the governance repo. > > Thanks and have a happy Memorial Day! > Matt +1 _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From jay.rhine at nokia.com Thu Jun 10 22:11:19 2021 From: jay.rhine at nokia.com (Rhine, Jay (Nokia - US)) Date: Thu, 10 Jun 2021 22:11:19 +0000 Subject: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Message-ID: Hello All! We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Fri Jun 11 18:07:57 2021 From: ashlee at openstack.org (ashlee at openstack.org) Date: Fri, 11 Jun 2021 18:07:57 +0000 Subject: [Airship-discuss] Updated invitation: Airship WC bi-weekly meeting @ Thu Jun 17, 2021 7:30pm - 8pm (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <0000000000003436e205c481630a@google.com> This event has been changed. Title: Airship WC bi-weekly meeting Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN When: Thu Jun 17, 2021 7:30pm – 8pm Central Time - Chicago (changed) Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Calendar: airship-discuss at lists.airshipit.org Who: * ashlee at openstack.org - organizer * rroodsari at mirantis.com * venugopal at kanumalla.com * airship-discuss at lists.airshipit.org Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=Xzg0cmo2YzFnODRwNGFiOWc2Z3JqMmI5azg1MWo0YjlvNmgyNGNiOWo4ZDBrOGMxaDZrcTQ4ZDFoNm9sbGtqcWY5bDZrYWhhazk1NzRlamlsOWwxNGFraHE3MG8zNGM5cDZncjM2Y29fMjAyMTA2MTRUMTkwMDAwWiBhaXJzaGlwLWRpc2N1c3NAbGlzdHMuYWlyc2hpcGl0Lm9yZw&tok=MjAjYXNobGVlQG9wZW5zdGFjay5vcmdjYzkzOTNiNTY3MWZjOTg2ODI4NmM1ZDVkYTY2OTFmOGFkNTc5MGNh&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3287 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3364 bytes Desc: not available URL: From ashlee at openstack.org Fri Jun 11 18:08:09 2021 From: ashlee at openstack.org (ashlee at openstack.org) Date: Fri, 11 Jun 2021 18:08:09 +0000 Subject: [Airship-discuss] Updated invitation: Airship WC bi-weekly meeting @ Thu Jun 17, 2021 7:30am - 8am (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <000000000000ee38ac05c481638a@google.com> This event has been changed. Title: Airship WC bi-weekly meeting Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN When: Thu Jun 17, 2021 7:30am – 8am Central Time - Chicago (changed) Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Calendar: airship-discuss at lists.airshipit.org Who: * ashlee at openstack.org - organizer * rroodsari at mirantis.com * venugopal at kanumalla.com * airship-discuss at lists.airshipit.org Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=Xzg0cmo2YzFnODRwNGFiOWc2Z3JqMmI5azg1MWo0YjlvNmgyNGNiOWo4ZDBrOGMxaDZrcTQ4ZDFoNm9sbGtqcWY5bDZrYWhhazk1NzRlamlsOWwxNGFraHE3MG8zNGM5cDZncjM2Y29fMjAyMTA2MTRUMTkwMDAwWiBhaXJzaGlwLWRpc2N1c3NAbGlzdHMuYWlyc2hpcGl0Lm9yZw&tok=MjAjYXNobGVlQG9wZW5zdGFjay5vcmdjYzkzOTNiNTY3MWZjOTg2ODI4NmM1ZDVkYTY2OTFmOGFkNTc5MGNh&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3287 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3364 bytes Desc: not available URL: From ashlee at openstack.org Fri Jun 11 18:09:18 2021 From: ashlee at openstack.org (ashlee at openstack.org) Date: Fri, 11 Jun 2021 18:09:18 +0000 Subject: [Airship-discuss] Updated invitation: Airship TC bi-weekly meeting @ Every 2 weeks from 8am to 9am on Monday (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <00000000000005811705c48168d5@google.com> This event has been changed. Title: Airship TC bi-weekly meeting (changed) Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN When: Every 2 weeks from 8am to 9am on Monday Central Time - Chicago (changed) Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Calendar: airship-discuss at lists.airshipit.org Who: * ashlee at openstack.org - organizer * airship-discuss at lists.airshipit.org * rroodsari at mirantis.com * venugopal at kanumalla.com Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=Xzg0cmo2YzFnODRwNGFiOWc2Z3JqMmI5azg1MWo0YjlvNmgyNGNiOWo4ZDBrOGMxaDZrcTQ4ZDFoNm9sbGtqcWY5bDZrYWhhazk1NzRlamlsOWwxNGFraHE3MG8zNGM5cDZncjM2Y28gYWlyc2hpcC1kaXNjdXNzQGxpc3RzLmFpcnNoaXBpdC5vcmc&tok=MjAjYXNobGVlQG9wZW5zdGFjay5vcmdkZGEzMDU0ZWEzMThjNDg4MTlmMDYwY2I4NTlkZDM3ZWEwY2I5MWE4&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3256 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3332 bytes Desc: not available URL: From ashlee at openstack.org Fri Jun 11 18:09:19 2021 From: ashlee at openstack.org (ashlee at openstack.org) Date: Fri, 11 Jun 2021 18:09:19 +0000 Subject: [Airship-discuss] Invitation: Airship WC bi-weekly meeting @ Thu Jun 17, 2021 7:30am - 8am (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <00000000000018e3e605c48168f7@google.com> You have been invited to the following event. Title: Airship WC bi-weekly meeting Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN When: Thu Jun 17, 2021 7:30am – 8am Central Time - Chicago Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Calendar: airship-discuss at lists.airshipit.org Who: * ashlee at openstack.org - organizer * rroodsari at mirantis.com * airship-discuss at lists.airshipit.org * venugopal at kanumalla.com Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=XzZrcGphZ2hoNm9vajJiYTQ2MHAzZ2I5azg4cWs4YjlvOGNyM2liYTM2a3BqOGNocDg0cjMyZ3BsNjRfMjAyMTA2MTRUMTkwMDAwWiBhaXJzaGlwLWRpc2N1c3NAbGlzdHMuYWlyc2hpcGl0Lm9yZw&tok=MjAjYXNobGVlQG9wZW5zdGFjay5vcmc0MDEyMDdhYjJjOWQ2ZTgxMDMwNDYxZTcyYzI0OTIzZDhlY2VhYzcy&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2651 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2706 bytes Desc: not available URL: From ashlee at openstack.org Fri Jun 11 18:09:19 2021 From: ashlee at openstack.org (ashlee at openstack.org) Date: Fri, 11 Jun 2021 18:09:19 +0000 Subject: [Airship-discuss] Invitation: Airship WC bi-weekly meeting @ Every 2 weeks from 2pm to 3pm on Monday from Mon Feb 22 to Mon Jun 28 (CST) (airship-discuss@lists.airshipit.org) Message-ID: <00000000000017bf2205c48168d6@google.com> You have been invited to the following event. Title: Airship WC bi-weekly meeting Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN When: Every 2 weeks from 2pm to 3pm on Monday from Mon Feb 22 to Mon Jun 28 Central Time - Chicago Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Calendar: airship-discuss at lists.airshipit.org Who: * ashlee at openstack.org - organizer * rroodsari at mirantis.com * airship-discuss at lists.airshipit.org * venugopal at kanumalla.com Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=XzZrcGphZ2hoNm9vajJiYTQ2MHAzZ2I5azg4cWs4YjlvOGNyM2liYTM2a3BqOGNocDg0cjMyZ3BsNjQgYWlyc2hpcC1kaXNjdXNzQGxpc3RzLmFpcnNoaXBpdC5vcmc&tok=MjAjYXNobGVlQG9wZW5zdGFjay5vcmc1ODYyYmZlZjc3MThlOTAyYzE0NTUyZmRlNjlhYjM0Nzg5ZmM5ODZl&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3048 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3120 bytes Desc: not available URL: From jay.rhine at nokia.com Mon Jun 14 15:57:54 2021 From: jay.rhine at nokia.com (Rhine, Jay (Nokia - US)) Date: Mon, 14 Jun 2021 15:57:54 +0000 Subject: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? In-Reply-To: References: Message-ID: Hello! I sent this after normal working hours for same last week, so I'll resend this request again ... any ideas are appreciated. We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: Rhine, Jay (Nokia - US) Sent: Thursday, June 10, 2021 6:11 PM To: airship-discuss at lists.airshipit.org Subject: Kubernetes Certificates Expiring, how to renew in Airship? Hello All! We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ab7180 at att.com Thu Jun 17 19:45:01 2021 From: ab7180 at att.com (BOSE, ARIJIT) Date: Thu, 17 Jun 2021 19:45:01 +0000 Subject: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? In-Reply-To: References: Message-ID: Hello Jay, Hope you are doing good. We don't have the cert-rotation scripts ready for upstream. We shall share some steps to rotate the K8s certs shortly. Also would request you to check the ingress cert expiration dates. BR, Arijit Bose From: Rhine, Jay (Nokia - US) Sent: Monday, June 14, 2021 10:58 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello! I sent this after normal working hours for same last week, so I'll resend this request again ... any ideas are appreciated. We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: Rhine, Jay (Nokia - US) Sent: Thursday, June 10, 2021 6:11 PM To: airship-discuss at lists.airshipit.org Subject: Kubernetes Certificates Expiring, how to renew in Airship? Hello All! We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jay.rhine at nokia.com Thu Jun 17 20:08:52 2021 From: jay.rhine at nokia.com (Rhine, Jay (Nokia - US)) Date: Thu, 17 Jun 2021 20:08:52 +0000 Subject: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? In-Reply-To: References: Message-ID: Hello! Our ingress certs expire often and we know how to replace them, but the system ones we are not sure on. If you can share those steps, it would be great. Thanks, Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: BOSE, ARIJIT Sent: Thursday, June 17, 2021 3:45 PM To: Rhine, Jay (Nokia - US) ; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello Jay, Hope you are doing good. We don't have the cert-rotation scripts ready for upstream. We shall share some steps to rotate the K8s certs shortly. Also would request you to check the ingress cert expiration dates. BR, Arijit Bose From: Rhine, Jay (Nokia - US) > Sent: Monday, June 14, 2021 10:58 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello! I sent this after normal working hours for same last week, so I'll resend this request again ... any ideas are appreciated. We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: Rhine, Jay (Nokia - US) Sent: Thursday, June 10, 2021 6:11 PM To: airship-discuss at lists.airshipit.org Subject: Kubernetes Certificates Expiring, how to renew in Airship? Hello All! We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Fri Jun 18 20:54:19 2021 From: ashlee at openstack.org (ashlee at openstack.org) Date: Fri, 18 Jun 2021 20:54:19 +0000 Subject: [Airship-discuss] Updated invitation: Airship TC bi-weekly meeting @ Every 2 weeks from 10am to 11am on Monday (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <0000000000000a682805c51087fe@google.com> This event has been changed. Title: Airship TC bi-weekly meeting Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN When: Every 2 weeks from 10am to 11am on Monday Central Time - Chicago (changed) Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Calendar: airship-discuss at lists.airshipit.org Who: * ashlee at openstack.org - organizer * airship-discuss at lists.airshipit.org * rroodsari at mirantis.com * venugopal at kanumalla.com Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=Xzg0cmo2YzFnODRwNGFiOWc2Z3JqMmI5azg1MWo0YjlvNmgyNGNiOWo4ZDBrOGMxaDZrcTQ4ZDFoNm9sbGtqcWY5bDZrYWhhazk1NzRlamlsOWwxNGFraHE3MG8zNGM5cDZncjM2Y28gYWlyc2hpcC1kaXNjdXNzQGxpc3RzLmFpcnNoaXBpdC5vcmc&tok=MjAjYXNobGVlQG9wZW5zdGFjay5vcmdkZGEzMDU0ZWEzMThjNDg4MTlmMDYwY2I4NTlkZDM3ZWEwY2I5MWE4&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3249 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3325 bytes Desc: not available URL: From ab7180 at att.com Sun Jun 20 05:01:24 2021 From: ab7180 at att.com (BOSE, ARIJIT) Date: Sun, 20 Jun 2021 05:01:24 +0000 Subject: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? In-Reply-To: References: Message-ID: Hello Jay, You can try using the below procedure to manually rotate the certificates for the Airship1 cluster. https://review.opendev.org/c/airship/treasuremap/+/797183/1/tools/brownfield/Manual-Cert-Rotation.md BR, Arijit Bose From: Rhine, Jay (Nokia - US) Sent: Thursday, June 17, 2021 3:09 PM To: BOSE, ARIJIT ; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello! Our ingress certs expire often and we know how to replace them, but the system ones we are not sure on. If you can share those steps, it would be great. Thanks, Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: BOSE, ARIJIT > Sent: Thursday, June 17, 2021 3:45 PM To: Rhine, Jay (Nokia - US) >; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello Jay, Hope you are doing good. We don't have the cert-rotation scripts ready for upstream. We shall share some steps to rotate the K8s certs shortly. Also would request you to check the ingress cert expiration dates. BR, Arijit Bose From: Rhine, Jay (Nokia - US) > Sent: Monday, June 14, 2021 10:58 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello! I sent this after normal working hours for same last week, so I'll resend this request again ... any ideas are appreciated. We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: Rhine, Jay (Nokia - US) Sent: Thursday, June 10, 2021 6:11 PM To: airship-discuss at lists.airshipit.org Subject: Kubernetes Certificates Expiring, how to renew in Airship? Hello All! We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don't think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jay.rhine at nokia.com Sun Jun 20 20:57:19 2021 From: jay.rhine at nokia.com (Rhine, Jay (Nokia - US)) Date: Sun, 20 Jun 2021 20:57:19 +0000 Subject: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? In-Reply-To: References: , Message-ID: Thank you! We will give this a try ---- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com Home Office - 732-930-0380 ________________________________ From: BOSE, ARIJIT Sent: Sunday, June 20, 2021 1:01:24 AM To: Rhine, Jay (Nokia - US) ; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello Jay, You can try using the below procedure to manually rotate the certificates for the Airship1 cluster. https://review.opendev.org/c/airship/treasuremap/+/797183/1/tools/brownfield/Manual-Cert-Rotation.md BR, Arijit Bose From: Rhine, Jay (Nokia - US) Sent: Thursday, June 17, 2021 3:09 PM To: BOSE, ARIJIT ; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello! Our ingress certs expire often and we know how to replace them, but the system ones we are not sure on. If you can share those steps, it would be great. Thanks, Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: BOSE, ARIJIT > Sent: Thursday, June 17, 2021 3:45 PM To: Rhine, Jay (Nokia - US) >; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello Jay, Hope you are doing good. We don’t have the cert-rotation scripts ready for upstream. We shall share some steps to rotate the K8s certs shortly. Also would request you to check the ingress cert expiration dates. BR, Arijit Bose From: Rhine, Jay (Nokia - US) > Sent: Monday, June 14, 2021 10:58 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Kubernetes Certificates Expiring, how to renew in Airship? Hello! I sent this after normal working hours for same last week, so I’ll resend this request again … any ideas are appreciated. We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don’t think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com From: Rhine, Jay (Nokia - US) Sent: Thursday, June 10, 2021 6:11 PM To: airship-discuss at lists.airshipit.org Subject: Kubernetes Certificates Expiring, how to renew in Airship? Hello All! We have an airship system that we have been using, and we have noticed that many of the certificates in /etc/kubernetes will expire soon. In particular, these certificates: /etc/kubernetes/scheduler/scheduler.pem /etc/kubernetes/admin/pki/admin.pem /etc/kubernetes/controller-manager/controller-manager.pem /etc/kubernetes/apiserver/apiserver-proxy-cert.pem /etc/kubernetes/apiserver/pki/apiserver.pem /etc/kubernetes/apiserver/pki/apiserver-both.pem /etc/kubernetes/apiserver/pki/etcd-client.pem /etc/kubernetes/apiserver/pki/kubelet-client.pem /etc/kubernetes/pki/kubelet.pem Is there a procedure, script, or guidance on how we can renew those certificates? We looked around online a bit, and the generic procedures seemed to mostly refer to kubeadm, which I don’t think is being used by airship. Any suggestions would be appreciated. Thank you! Jay --- Jay Rhine, CISSP DMTS, Solution Validation Global Services Center Nokia Software, Nokia Email - Jay.Rhine at nokia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Jun 23 14:04:38 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 23 Jun 2021 14:04:38 +0000 Subject: [Airship-discuss] Design Meetings during Summer Months Message-ID: <0F87C705-0227-44C3-8B16-61D580023DDA@att.com> All, We want to reduce the incidence of the Design Meetings to once a week. Please vote on this pool to select which day of the week we continue holding the design meetings during the summer months. https://doodle.com/poll/pg69vtu635q4a5cx?utm_source=poll&utm_medium=link Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From anyrude10 at gmail.com Wed Jun 23 11:10:46 2021 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Wed, 23 Jun 2021 16:40:46 +0530 Subject: [Airship-discuss] Airship Seaworthy Installation Message-ID: Hi Team, I am planning to install Airship Seaworthy for which I have arranged 6 hardwares as mentioned in the below link: https://docs.airshipit.org/treasuremap/seaworthy.html However, I am unable to find the Installation Document/ Deployment Guide There is no deployment guide available in the link below: https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html Is this project supporting installation of Seaworthy in the Production Environment? Please share the link where I can find the deployment steps. Looking forward to hearing from you. Regards Anirudh Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji5690 at att.com Wed Jun 23 17:00:40 2021 From: ji5690 at att.com (GU, JAMES) Date: Wed, 23 Jun 2021 17:00:40 +0000 Subject: [Airship-discuss] Airship Seaworthy Installation In-Reply-To: References: Message-ID: Hello Anirudh, The Airship 1 site authoring and deployment guide is at this link: https://docs.airshipit.org/treasuremap/authoring_and_deployment.html. It appears that quite a few links in https://docs.airshipit.org/treasuremap/seaworthy.html to the documents and source code have been out dated. Do you mind raising an issue to have them fixed? Just a note that the above link is for Airship 1. The latest release is Airship 2 and its site authoring and deployment guide is at: https://docs.airshipit.org/airship2/baremetal.html. Thanks, James From: Anirudh Gupta Sent: Wednesday, June 23, 2021 4:11 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship Seaworthy Installation Hi Team, I am planning to install Airship Seaworthy for which I have arranged 6 hardwares as mentioned in the below link: https://docs.airshipit.org/treasuremap/seaworthy.html However, I am unable to find the Installation Document/ Deployment Guide There is no deployment guide available in the link below: https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html Is this project supporting installation of Seaworthy in the Production Environment? Please share the link where I can find the deployment steps. Looking forward to hearing from you. Regards Anirudh Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Jun 24 16:12:08 2021 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 24 Jun 2021 16:12:08 +0000 Subject: [Airship-discuss] Airship TC bi-weekly meeting Message-ID: Team, I won’t be able to make the TC meeting next week. Since we don’t have any topics on the agenda, any objections if we cancel this one and pick it back up on the 12th? At that meeting we’ll want to start geting ready for the TC elections in August. Thanks, Matt -----Original Appointment----- From: ashlee at openstack.org Sent: Wednesday, February 26, 2020 4:32 PM To: ashlee at openstack.org; airship-discuss at lists.airshipit.org; rroodsari at mirantis.com; venugopal at kanumalla.com Subject: Airship TC bi-weekly meeting When: Monday, June 28, 2021 10:00 AM-11:00 AM America/Chicago. Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 This event has been changed. Airship TC bi-weekly meeting When Changed: Every 2 weeks from 10am to 11am on Monday Central Time - Chicago Where https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 (map) Calendar airship-discuss at lists.airshipit.org Who • ashlee at openstack.org - organizer • airship-discuss at lists.airshipit.org • rroodsari at mirantis.com • venugopal at kanumalla.com more details » Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN Going (airship-discuss at lists.airshipit.org)? All events in this series: Yes - Maybe - No more options » Invitation from Google Calendar You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ab805p at att.com Thu Jun 24 16:21:03 2021 From: ab805p at att.com (BAILEY, ALEXANDER) Date: Thu, 24 Jun 2021 16:21:03 +0000 Subject: [Airship-discuss] Airship TC bi-weekly meeting In-Reply-To: References: Message-ID: Matt, I agree, let’s reconvene on the 12th. Regards, Alex Bailey From: MCEUEN, MATT Sent: Thursday, June 24, 2021 11:12 AM To: airship-discuss at lists.airshipit.org Cc: ashlee at openstack.org Subject: Re: [Airship-discuss] Airship TC bi-weekly meeting ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Team, I won’t be able to make the TC meeting next week. Since we don’t have any topics on the agenda, any objections if we cancel this one and pick it back up on the 12th? At that meeting we’ll want to start geting ready for the TC elections in August. Thanks, Matt -----Original Appointment----- From: ashlee at openstack.org > Sent: Wednesday, February 26, 2020 4:32 PM To: ashlee at openstack.org; airship-discuss at lists.airshipit.org; rroodsari at mirantis.com; venugopal at kanumalla.com Subject: Airship TC bi-weekly meeting When: Monday, June 28, 2021 10:00 AM-11:00 AM America/Chicago. Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 This event has been changed. Airship TC bi-weekly meeting When Changed: Every 2 weeks from 10am to 11am on Monday Central Time - Chicago Where https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 (map) Calendar airship-discuss at lists.airshipit.org Who • ashlee at openstack.org - organizer • airship-discuss at lists.airshipit.org • rroodsari at mirantis.com • venugopal at kanumalla.com more details » Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN Going (airship-discuss at lists.airshipit.org)? All events in this series: Yes - Maybe - No more options » Invitation from Google Calendar You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Fri Jun 25 19:49:42 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 25 Jun 2021 19:49:42 +0000 Subject: [Airship-discuss] Canceled: Tuesday Airship Open Design Discussions Message-ID: Canceling Tuesday Meetings for the time been. Meetings Topics can be found at : https://hackmd.io/QiEksO4fRk-MnBjwBFaAkQ Airship Notes : https://hackmd.io/team/airship?nav=overview ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,928172342# United States, Houston Phone Conference ID: 928 172 342# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 8154 bytes Desc: not available URL: From anyrude10 at gmail.com Mon Jun 28 11:11:26 2021 From: anyrude10 at gmail.com (Anirudh Gupta) Date: Mon, 28 Jun 2021 16:41:26 +0530 Subject: [Airship-discuss] Airship Seaworthy Installation In-Reply-To: References: Message-ID: Hi, Thanks for the response. I have gone through the Airship 2 documentation and it seems to be very promising. Currently we are looking to deploy the tool in the Production Environment? Is Airship 2 suitable for Production? Is there any other model (like seaworthy) with which we deploy Airship in Production? Regards Anirudh Gupta On Wed, Jun 23, 2021 at 10:31 PM GU, JAMES wrote: > Hello Anirudh, > > > > The Airship 1 site authoring and deployment guide is at this link: > https://docs.airshipit.org/treasuremap/authoring_and_deployment.html. > > > > It appears that quite a few links in > https://docs.airshipit.org/treasuremap/seaworthy.html to the documents > and source code have been out dated. Do you mind raising an issue to have > them fixed? > > > > Just a note that the above link is for Airship 1. The latest release is > Airship 2 and its site authoring and deployment guide is at: > https://docs.airshipit.org/airship2/baremetal.html. > > > > Thanks, > > > > James > > > > *From:* Anirudh Gupta > *Sent:* Wednesday, June 23, 2021 4:11 AM > *To:* airship-discuss at lists.airshipit.org > *Subject:* [Airship-discuss] Airship Seaworthy Installation > > > > Hi Team, > > > > I am planning to install Airship Seaworthy for which I have arranged 6 > hardwares as mentioned in the below link: > > > > https://docs.airshipit.org/treasuremap/seaworthy.html > > > > > However, I am unable to find the Installation Document/ Deployment Guide > > > > There is no deployment guide available in the link below: > > > > > https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html > > > > > Is this project supporting installation of Seaworthy in the Production > Environment? > > Please share the link where I can find the deployment steps. > > > > Looking forward to hearing from you. > > > > Regards > > Anirudh Gupta > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Mon Jun 28 13:34:15 2021 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 28 Jun 2021 13:34:15 +0000 Subject: [Airship-discuss] Airship TC bi-weekly meeting Message-ID: Reminder, today’s TC meeting is cancelled. We’ll pick back up next time. -----Original Appointment----- From: ashlee at openstack.org Sent: Wednesday, February 26, 2020 4:32 PM To: ashlee at openstack.org; airship-discuss at lists.airshipit.org; rroodsari at mirantis.com; venugopal at kanumalla.com Subject: Airship TC bi-weekly meeting When: Monday, June 28, 2021 10:00 AM-11:00 AM America/Chicago. Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 This event has been changed. Airship TC bi-weekly meeting When Changed: Every 2 weeks from 10am to 11am on Monday Central Time - Chicago Where https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 (map) Calendar airship-discuss at lists.airshipit.org Who • ashlee at openstack.org - organizer • airship-discuss at lists.airshipit.org • rroodsari at mirantis.com • venugopal at kanumalla.com more details » Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN Going (airship-discuss at lists.airshipit.org)? All events in this series: Yes - Maybe - No more options » Invitation from Google Calendar You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Mon Jun 28 14:22:58 2021 From: ashlee at openstack.org (ashlee at openstack.org) Date: Mon, 28 Jun 2021 14:22:58 +0000 Subject: [Airship-discuss] Updated invitation: Airship TC bi-weekly meeting @ Every 2 weeks from 10am to 11am on Monday except Mon Jun 28 10am (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <000000000000ddc59d05c5d439c8@google.com> This event has been changed. Title: Airship TC bi-weekly meeting Agenda: https://etherpad.opendev.org/p/airship-wc-meeting Join Zoom Meeting https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Meeting ID: 972 571 7388 Passcode: airshipit One tap mobile +13462487799,,9725717388# US (Houston) +12532158782,,9725717388# US (Tacoma) Dial by your location +1 346 248 7799 US (Houston) +1 253 215 8782 US (Tacoma) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) Meeting ID: 972 571 7388 Find your local number: https://zoom.us/u/aSLnCZKKN When: Every 2 weeks from 10am to 11am on Monday except Mon Jun 28 10am Central Time - Chicago (changed) Where: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09 Calendar: airship-discuss at lists.airshipit.org Who: * ashlee at openstack.org - organizer * airship-discuss at lists.airshipit.org * rroodsari at mirantis.com * venugopal at kanumalla.com Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=Xzg0cmo2YzFnODRwNGFiOWc2Z3JqMmI5azg1MWo0YjlvNmgyNGNiOWo4ZDBrOGMxaDZrcTQ4ZDFoNm9sbGtqcWY5bDZrYWhhazk1NzRlamlsOWwxNGFraHE3MG8zNGM5cDZncjM2Y28gYWlyc2hpcC1kaXNjdXNzQGxpc3RzLmFpcnNoaXBpdC5vcmc&tok=MjAjYXNobGVlQG9wZW5zdGFjay5vcmdkZGEzMDU0ZWEzMThjNDg4MTlmMDYwY2I4NTlkZDM3ZWEwY2I5MWE4&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3290 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3367 bytes Desc: not available URL: From ashlee at openstack.org Tue Jun 29 14:12:20 2021 From: ashlee at openstack.org (Ashlee Ferguson) Date: Tue, 29 Jun 2021 09:12:20 -0500 Subject: [Airship-discuss] October 2021 PTG Dates & Registration Message-ID: <05081016-72E3-4BC6-A21C-4366BAA22EFC@openstack.org> Hi everyone, We're happy to announce the next virtual PTG[1] will take place October 18-22, 2021! Registration is now open[2]. The virtual PTG is free to attend, but make sure to register so you recieve important communications like schedules, passwords, and other relevant updates. Next week, keep an eye out for info regarding team sign-ups. Can't wait to see you all there! Ashlee [1] https://www.openstack.org/ptg/ [2] https://openinfra-ptg.eventbrite.com From rp2723 at att.com Tue Jun 29 14:08:11 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 29 Jun 2021 14:08:11 +0000 Subject: [Airship-discuss] Flight Plan - June 30 , 2021 - Cancelled Message-ID: <29B11E54-8C1F-4BB1-8DC7-FCE3C42C2398@att.com> All Need to cancel Flight Plan tomorrow. Most of us have another meeting we need to attend. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Wed Jun 30 12:47:04 2021 From: amy at demarco.com (Amy Marrich) Date: Wed, 30 Jun 2021 07:47:04 -0500 Subject: [Airship-discuss] [Diversity] Diversity and Inclusion July Meeting Update Message-ID: Due to most US companies having July 5th off, we will be moving the Jully D&I WG meeting Please join us Monday, July 19th at 17:00 UTC in the #openinfra-diversity channel on OFTC. The agenda can be found at https://etherpad.openstack.org/p/ diversity-wg-agenda. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Jun 29 14:06:50 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 29 Jun 2021 14:06:50 +0000 Subject: [Airship-discuss] Canceled: Airship Flight Plan Message-ID: Agenda and Topics at https://hackmd.io/93_0K4AAR9izrEpuDMa5Rw * Issues Review * Release Planning * Other Project Administrivia discussions ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,616265078# United States, Houston Phone Conference ID: 616 265 078# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 6871 bytes Desc: not available URL: From rp2723 at att.com Wed Jun 30 17:39:35 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 30 Jun 2021 17:39:35 +0000 Subject: [Airship-discuss] Thursday July 1st, 2021 - Design Meeting Cancelled Message-ID: <23E764FF-EE79-4548-A33C-018C11CD61D7@att.com> All The Design Meeting for Tomorrow is cancelled. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Jun 30 17:31:55 2021 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 30 Jun 2021 17:31:55 +0000 Subject: [Airship-discuss] Canceled: Thursday Airship Design Meeting Message-ID: Canceling this meeting, given potential overlaps for many. Design Topics or Agenda https://hackmd.io/QiEksO4fRk-MnBjwBFaAkQ Recordings https://hackmd.io/CvuF8MzmR9KPqyAePnilPQ ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting Or call in (audio only) +1 346-200-6580,,127354383# United States, Houston Phone Conference ID: 127 354 383# Find a local number | Reset PIN Learn More | Meeting options ________________________________________________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 8148 bytes Desc: not available URL: